Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Line 1, Column 146:
Attribute "class" exists, but can not be used for this element.
…<html lang="en" xml:lang="en" class="en" xmlns:fb="http://www.facebook.com/20You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 1, Column 110:
Missing xmlns attribute for element html.
The value should be: http://www.w3.org/1999/xhtml
…rg/TR/xhtml1/DTD/xhtml1-strict.dtd"><html lang="en" xml:lang="en" class="en"
Many Document Types based on XML need a mandatory xmlns="" on the root element. For example, the root element for XHTML will look like:
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
Line 7, Column 70:
element "esi:vars" undefined
…ico" rel="shortcut icon" /><esi:vars><script type="text/javascript">var sponsYou have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
Line 7, Column 251:
syntax of attribute value does not conform to declared value
…/script></esi:vars></head><body id=""><div id="ThirdPartyTrackers"><script ty
The value of an attribute contained something that is not allowed by
the specified syntax for that type of attribute. For instance, the
“selected” attribute must be
either minimized as “selected”
or spelled out in full as “selected="selected"”; the variant
“selected=""” is not allowed.
Line 7, Column 1486:
Attribute "target" exists, but can not be used for this element.
…<a href="http://ca.msn.com/" target="_blank"><img src="/img/template/poweredbYou have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 7, Column 1568:
required attribute "alt" not specified
…_logo.jpg" width="130" height="40" /></a><a href="/get-games-ready/index.htmlThe attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 7, Column 1708:
required attribute "alt" not specified
…r_logo.jpg" width="95" height="25" /></a></div><div id="ctvo_SearchForm"><divThe attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 7, Column 2298:
Attribute "language" exists, but can not be used for this element.
…s=''"> </div></div><script language="javascript" type="text/javascript">ManagYou have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 10, Column 132:
Attribute "size" exists, but can not be used for this element.
…"display:none"><fb:profile-pic size="square" width="21px" height="21px" facebYou have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 10, Column 147:
Attribute "width" exists, but can not be used for this element.
…<fb:profile-pic size="square" width="21px" height="21px" facebook-logo="true"You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 10, Column 161:
Attribute "height" exists, but can not be used for this element.
…c size="square" width="21px" height="21px" facebook-logo="true" uid="loggedinYou have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 10, Column 182:
Attribute "facebook-logo" is not a valid attribute
…="21px" height="21px" facebook-logo="true" uid="loggedinuser" linked="false">You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 10, Column 193:
Attribute "uid" is not a valid attribute. Did you mean "http-equiv" or "width"?
…ght="21px" facebook-logo="true" uid="loggedinuser" linked="false"> </fb:profiYou have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 10, Column 215:
Attribute "linked" is not a valid attribute. Did you mean "vlink" or "alink"?
…go="true" uid="loggedinuser" linked="false"> </fb:profile-pic></div><div id="You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 10, Column 222:
element "fb:profile-pic" undefined
…e" uid="loggedinuser" linked="false"> </fb:profile-pic></div><div id="fb_faviYou have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
Line 10, Column 302:
Attribute "background" exists, but can not be used for this element.
…_login"><fb:login-button background="dark" onlogin="FBConnect.OnLogin();" sizYou have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 10, Column 317:
Attribute "onlogin" is not a valid attribute. Did you mean "scrolling" or "onload"?
…in-button background="dark" onlogin="FBConnect.OnLogin();" size="medium" lengYou have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 10, Column 345:
Attribute "size" exists, but can not be used for this element.
…onlogin="FBConnect.OnLogin();" size="medium" length="short"> </fb:login-buttoYou have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 10, Column 361:
Attribute "length" is not a valid attribute. Did you mean "maxlength" or "content"?
…ct.OnLogin();" size="medium" length="short"> </fb:login-button></div><script You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 10, Column 368:
element "fb:login-button" undefined
…gin();" size="medium" length="short"> </fb:login-button></div><script type="tYou have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
Line 13, Column 176:
document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
…ext-align:center;font-color:#AA1B31'><strong><a href='http://get.adobe.com/flThe mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 17, Column 189:
document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
…0x90;ord=123456789?" target="_blank"><img src="http://ad.doubleclick.net/ad/cThe mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 19, Column 189:
document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
…0x90;ord=123456789?" target="_blank"><img src="http://ad.doubleclick.net/ad/cThe mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 21, Column 189:
document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
…0x90;ord=123456789?" target="_blank"><img src="http://ad.doubleclick.net/ad/cThe mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 24, Column 324:
required attribute "action" not specified
…hortCut"><form id="ctvo_FormChoices"><div class="" onmouseover="$(this).addClThe attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 24, Column 1438:
document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
…lick="myMenu.saveComboShortcuts()" /><input style="display:none" type="buttonThe mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 24, Column 1549:
document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
…ndo" onclick="myMenu.undoChoice()" /><input style="display:none" type="buttonThe mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 24, Column 1663:
document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
…et" onclick="myMenu.resetChoice()" /></form></div></div> </div></div><script The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 46, Column 111:
value of attribute "id" invalid: "1" cannot start a name
…floatLeft "><div class="hslice "id="1">
It is possible that you violated the naming convention for this attribute.
For example, id and name attributes must begin with
a letter, not a digit.
Line 50, Column 120:
document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
…ext-align:center;font-color:#AA1B31'><strong><a href='http://get.adobe.com/flThe mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 51, Column 267:
reference not terminated by REFC delimiter
…ewsreaderconfig/Config_home.xml&lang=E&environment=2&test=1&target_blank=falsIf you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 51, Column 270:
cannot generate system identifier for general entity "environment"
…readerconfig/Config_home.xml&lang=E&environment=2&test=1&target_blank=false',An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
Line 51, Column 270:
general entity "environment" not defined and no default entity
…readerconfig/Config_home.xml&lang=E&environment=2&test=1&target_blank=false',This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 51, Column 281:
reference not terminated by REFC delimiter
…g/Config_home.xml&lang=E&environment=2&test=1&target_blank=false','flash38775If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 51, Column 281:
reference to entity "environment" for which no system identifier could be generated
…g/Config_home.xml&lang=E&environment=2&test=1&target_blank=false','flash38775This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 51, Column 268:
entity was defined here
…wsreaderconfig/Config_home.xml&lang=E&environment=2&test=1&target_blank=false…onfig_home.xml&lang=E&environment=2&test=1&target_blank=false','flash3877558aAn entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
Line 51, Column 284:
general entity "test" not defined and no default entity
…onfig_home.xml&lang=E&environment=2&test=1&target_blank=false','flash3877558aThis is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 51, Column 288:
reference not terminated by REFC delimiter
…g_home.xml&lang=E&environment=2&test=1&target_blank=false','flash3877558a61b0If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 51, Column 288:
reference to entity "test" for which no system identifier could be generated
…g_home.xml&lang=E&environment=2&test=1&target_blank=false','flash3877558a61b0This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 51, Column 282:
entity was defined here
…/Config_home.xml&lang=E&environment=2&test=1&target_blank=false','flash387755…ome.xml&lang=E&environment=2&test=1&target_blank=false','flash3877558a61b04f2An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
Line 51, Column 291:
general entity "target_blank" not defined and no default entity
…ome.xml&lang=E&environment=2&test=1&target_blank=false','flash3877558a61b04f2This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 51, Column 303:
reference not terminated by REFC delimiter
…=E&environment=2&test=1&target_blank=false','flash3877558a61b04f23b7d7c94932dIf you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 51, Column 303:
reference to entity "target_blank" for which no system identifier could be generated
…=E&environment=2&test=1&target_blank=false','flash3877558a61b04f23b7d7c94932dThis is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 51, Column 289:
entity was defined here
…_home.xml&lang=E&environment=2&test=1&target_blank=false','flash3877558a61b04…ext-align:center;font-color:#AA1B31'><strong><a href='http://get.adobe.com/flThe mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 56, Column 305:
document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
…ext-align:center;font-color:#AA1B31'><strong><a href='http://get.adobe.com/flThe mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 57, Column 385:
reference not terminated by REFC delimiter
…eatured_photogalleries_home.xml&lang=E&environment=2&test=1','flash4c1aaf9bc1If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 57, Column 399:
reference not terminated by REFC delimiter
…alleries_home.xml&lang=E&environment=2&test=1','flash4c1aaf9bc1f94a07827c0092If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 57, Column 399:
reference to entity "environment" for which no system identifier could be generated
…alleries_home.xml&lang=E&environment=2&test=1','flash4c1aaf9bc1f94a07827c0092This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 51, Column 268:
entity was defined here
…wsreaderconfig/Config_home.xml&lang=E&environment=2&test=1&target_blank=false…s_home.xml&lang=E&environment=2&test=1','flash4c1aaf9bc1f94a07827c0092a781413If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 57, Column 406:
reference to entity "test" for which no system identifier could be generated
…s_home.xml&lang=E&environment=2&test=1','flash4c1aaf9bc1f94a07827c0092a781413This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 51, Column 282:
entity was defined here
…/Config_home.xml&lang=E&environment=2&test=1&target_blank=false','flash387755…a/index.html"><div class="ctvo_flag"><img src="/imgml/flags/roundedFlags/37x3The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 58, Column 4489:
document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
…a/index.html"><div class="ctvo_flag"><img src="/imgml/flags/roundedFlags/37x3The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 58, Column 6023:
document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
…a/index.html"><div class="ctvo_flag"><img src="/imgml/flags/roundedFlags/37x3The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 58, Column 7147:
document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
…a/index.html"><div class="ctvo_flag"><img src="/imgml/flags/roundedFlags/37x3The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 58, Column 8681:
document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
…a/index.html"><div class="ctvo_flag"><img src="/imgml/flags/roundedFlags/37x3The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 58, Column 9801:
document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
…a/index.html"><div class="ctvo_flag"><img src="/imgml/flags/roundedFlags/37x3The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 58, Column 11334:
document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
…a/index.html"><div class="ctvo_flag"><img src="/imgml/flags/roundedFlags/37x3The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 58, Column 12454:
document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
…a/index.html"><div class="ctvo_flag"><img src="/imgml/flags/roundedFlags/37x3The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 58, Column 13979:
document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
…a/index.html"><div class="ctvo_flag"><img src="/imgml/flags/roundedFlags/37x3The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 58, Column 15096:
document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
…a/index.html"><div class="ctvo_flag"><img src="/imgml/flags/roundedFlags/37x3The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 58, Column 16621:
document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
…a/index.html"><div class="ctvo_flag"><img src="/imgml/flags/roundedFlags/37x3The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 58, Column 17739:
document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
…a/index.html"><div class="ctvo_flag"><img src="/imgml/flags/roundedFlags/37x3The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 58, Column 19261:
document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
…a/index.html"><div class="ctvo_flag"><img src="/imgml/flags/roundedFlags/37x3The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 58, Column 20354:
document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
…a/index.html"><div class="ctvo_flag"><img src="/imgml/flags/roundedFlags/37x3The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 58, Column 21829:
document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
…a/index.html"><div class="ctvo_flag"><img src="/imgml/flags/roundedFlags/37x3The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 58, Column 22925:
document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
…a/index.html"><div class="ctvo_flag"><img src="/imgml/flags/roundedFlags/37x3The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 58, Column 24403:
document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
…a/index.html"><div class="ctvo_flag"><img src="/imgml/flags/roundedFlags/37x3The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 58, Column 25501:
document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
…a/index.html"><div class="ctvo_flag"><img src="/imgml/flags/roundedFlags/37x3The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 58, Column 26981:
document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
…a/index.html"><div class="ctvo_flag"><img src="/imgml/flags/roundedFlags/37x3The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 58, Column 28101:
document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
…a/index.html"><div class="ctvo_flag"><img src="/imgml/flags/roundedFlags/37x3The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 58, Column 29620:
document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
…a/index.html"><div class="ctvo_flag"><img src="/imgml/flags/roundedFlags/37x3The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 58, Column 30728:
document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
…a/index.html"><div class="ctvo_flag"><img src="/imgml/flags/roundedFlags/37x3The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 58, Column 32237:
document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
…a/index.html"><div class="ctvo_flag"><img src="/imgml/flags/roundedFlags/37x3The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 58, Column 33344:
document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
…a/index.html"><div class="ctvo_flag"><img src="/imgml/flags/roundedFlags/37x3The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 58, Column 34680:
Attribute "widht" is not a valid attribute. Did you mean "width" or "marginwidth"?
…ow_dx.png" alt="" height="22" widht="18" style="cursor: pointer;" /> </div><sYou have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 67, Column 174:
document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
…x250;ord=123456789?" target="_blank"><img src="http://ad.doubleclick.net/ad/cThe mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 68, Column 108:
character "&" is the first character of a delimiter but occurred as data
…lass="ctvo_titleLeft"> </span>Blogs & Features<span class="ctvo_titleRight"> This message may appear in several cases:
Line 69, Column 13:
Attribute "mce_keep" is not a valid attribute
<P mce_keep="true"> </P> </div> </div> </div> <div class="ctvo_fourBoxes"><You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 69, Column 19:
element "P" undefined. Did you mean "p"?
<P mce_keep="true"> </P> </div> </div> </div> <div class="ctvo_fourBoxes"><You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
Line 69, Column 1795:
element "P" undefined. Did you mean "p"?
…ada, on display </strong></a></h3><P>Friday's openining ceremony showed the wYou have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
Line 74, Column 728:
end tag for "br" omitted, but OMITTAG NO was specified
… and A to find your hockey twin.<br> </div></li><li><a href="http://call.ctvoYou may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 74, Column 723:
start tag was here
…ive Q and A to find your hockey twin.<br> </div></li><li><a href="http://call…"><div class=""><div class=""><style>The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 76, Column 126:
document type does not allow element "style" here
…"><div class=""><div class=""><style>The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Line 104, Column 261:
required attribute "alt" not specified
…Games.jpg" width="163" height="95" /> </a> </div>The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 105, Column 242:
required attribute "alt" not specified
…ockey.jpg" width="163" height="95" /> </a> </div>The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 107, Column 100:
value of attribute "id" invalid: "2" cannot start a name
…="ctvo_box"><div class="hslice" id="2"><a rel="feedurl" href="/webslices/libr
It is possible that you violated the naming convention for this attribute.
For example, id and name attributes must begin with
a letter, not a digit.
Line 134, Column 688:
required attribute "alt" not specified
…/videopage/GetSirverlight_326.jpg" /></a></div><div class="with_background"><The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 134, Column 1075:
document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
…Text();"><div class="ctvo_thumbCntr"><img src="/mm//Photo/Generic/General/04/The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 134, Column 1629:
document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
…Text();"><div class="ctvo_thumbCntr"><img src="/mm//Photo/Sports/Events/04/09The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 134, Column 2143:
document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
…Text();"><div class="ctvo_thumbCntr"><img src="/mm//Photo/Sports/CTVO/04/09/9The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 134, Column 2562:
required attribute "alt" not specified
…mgml/follow.jpg" class="nextVideo" /></a> </div><div class="ctvo_videotext"><The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 138, Column 174:
document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
…x250;ord=123456789?" target="_blank"><img src="http://ad.doubleclick.net/ad/cThe mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 138, Column 406:
value of attribute "id" invalid: "4" cannot start a name
…iv class=""><div class="hslice" id="4"><a rel="feedurl" href="/webslices/libr
It is possible that you violated the naming convention for this attribute.
For example, id and name attributes must begin with
a letter, not a digit.
Line 140, Column 204:
document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
…x240;ord=123456789?" target="_blank"><img src="http://ad.doubleclick.net/ad/cThe mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 141, Column 375:
Attribute "name" exists, but can not be used for this element.
…nswers"><form id="f_poll41082" name="f_poll41082"><ul class="PollQAList"><li>You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 141, Column 388:
required attribute "action" not specified
… id="f_poll41082" name="f_poll41082"><ul class="PollQAList"><li><input class=The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 141, Column 477:
value of attribute "id" invalid: "4" cannot start a name
…" type="radio" name="i_answers" id="486" value="486" /><label for="486">Cindy
It is possible that you violated the naming convention for this attribute.
For example, id and name attributes must begin with
a letter, not a digit.
Line 141, Column 508:
value of attribute "for" invalid: "4" cannot start a name
… id="486" value="486" /><label for="486">Cindy Klassen </label></li><li><inpu
It is possible that you violated the naming convention for this attribute.
For example, id and name attributes must begin with
a letter, not a digit.
Line 141, Column 605:
value of attribute "id" invalid: "4" cannot start a name
…" type="radio" name="i_answers" id="487" value="487" /><label for="487">Alexa
It is possible that you violated the naming convention for this attribute.
For example, id and name attributes must begin with
a letter, not a digit.
Line 141, Column 636:
value of attribute "for" invalid: "4" cannot start a name
… id="487" value="487" /><label for="487">Alexandre Bilodeau </label></li><li>
It is possible that you violated the naming convention for this attribute.
For example, id and name attributes must begin with
a letter, not a digit.
Line 141, Column 738:
value of attribute "id" invalid: "4" cannot start a name
…" type="radio" name="i_answers" id="488" value="488" /><label for="488">Clara
It is possible that you violated the naming convention for this attribute.
For example, id and name attributes must begin with
a letter, not a digit.
Line 141, Column 769:
value of attribute "for" invalid: "4" cannot start a name
… id="488" value="488" /><label for="488">Clara Hughes </label></li><li class=
It is possible that you violated the naming convention for this attribute.
For example, id and name attributes must begin with
a letter, not a digit.
Line 141, Column 878:
value of attribute "id" invalid: "4" cannot start a name
…" type="radio" name="i_answers" id="490" value="490" /><label for="490">Krist
It is possible that you violated the naming convention for this attribute.
For example, id and name attributes must begin with
a letter, not a digit.
Line 141, Column 909:
value of attribute "for" invalid: "4" cannot start a name
… id="490" value="490" /><label for="490">Kristina Groves </label></li></ul><i
It is possible that you violated the naming convention for this attribute.
For example, id and name attributes must begin with
a letter, not a digit.
Line 141, Column 1124:
document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
…okie.setRaw('poll41082',41082,30)" /><input type="hidden" value="Please choosThe mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 141, Column 1207:
document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
…ption" id="message" name="message" /><esi:vars><input type="hidden" name="geoThe mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 141, Column 1217:
element "esi:vars" undefined
…"message" name="message" /><esi:vars><input type="hidden" name="geo_country" You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
Line 146, Column 105:
cannot generate system identifier for general entity "ThanksUrl"
…lack.html?ThanksText='+ThanksText+'&ThanksUrl='+ThanksUrl+'&rnd='+Math.randomAn entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
Line 146, Column 105:
general entity "ThanksUrl" not defined and no default entity
…lack.html?ThanksText='+ThanksText+'&ThanksUrl='+ThanksUrl+'&rnd='+Math.randomThis is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 146, Column 114:
reference not terminated by REFC delimiter
…?ThanksText='+ThanksText+'&ThanksUrl='+ThanksUrl+'&rnd='+Math.random(),{methoIf you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 146, Column 114:
reference to entity "ThanksUrl" for which no system identifier could be generated
…?ThanksText='+ThanksText+'&ThanksUrl='+ThanksUrl+'&rnd='+Math.random(),{methoThis is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 146, Column 103:
entity was defined here
…tBlack.html?ThanksText='+ThanksText+'&ThanksUrl='+ThanksUrl+'&rnd='+Math.rand…hanksText+'&ThanksUrl='+ThanksUrl+'&rnd='+Math.random(),{method: 'get'});$('rAn entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
Line 146, Column 129:
general entity "rnd" not defined and no default entity
…hanksText+'&ThanksUrl='+ThanksUrl+'&rnd='+Math.random(),{method: 'get'});$('rThis is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 146, Column 132:
reference not terminated by REFC delimiter
…ksText+'&ThanksUrl='+ThanksUrl+'&rnd='+Math.random(),{method: 'get'});$('resuIf you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 146, Column 132:
reference to entity "rnd" for which no system identifier could be generated
…ksText+'&ThanksUrl='+ThanksUrl+'&rnd='+Math.random(),{method: 'get'});$('resuThis is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 146, Column 127:
entity was defined here
…+ThanksText+'&ThanksUrl='+ThanksUrl+'&rnd='+Math.random(),{method: 'get'});$(…x100;ord=123456789?" target="_blank"><img src="http://ad.doubleclick.net/ad/cThe mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 152, Column 321:
Attribute "class" exists, but can not be used for this element.
…div class="fb_fanbox"><fb:fan class="FBFanWidgetSmall" profile_id="9161952952You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 152, Column 351:
Attribute "profile_id" is not a valid attribute. Did you mean "profile"?
…class="FBFanWidgetSmall" profile_id="91619529529" stream="0" connections="5" You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 152, Column 372:
Attribute "stream" is not a valid attribute. Did you mean "scheme" or "frameborder"?
…ll" profile_id="91619529529" stream="0" connections="5" width="326" height="1You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 152, Column 388:
Attribute "connections" is not a valid attribute
…91619529529" stream="0" connections="5" width="326" height="165"> </fb:fan> <You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 152, Column 398:
Attribute "width" exists, but can not be used for this element.
…9" stream="0" connections="5" width="326" height="165"> </fb:fan> </div><div You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 152, Column 411:
Attribute "height" exists, but can not be used for this element.
… connections="5" width="326" height="165"> </fb:fan> </div><div class="fb_fanYou have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 152, Column 416:
element "fb:fan" undefined
…ections="5" width="326" height="165"> </fb:fan> </div><div class="fb_fanfooteYou have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
Line 157, Column 174:
document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
…x100;ord=123456789?" target="_blank"><img src="http://ad.doubleclick.net/ad/cThe mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 159, Column 174:
document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
…x100;ord=123456789?" target="_blank"><img src="http://ad.doubleclick.net/ad/cThe mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 161, Column 174:
document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
…x100;ord=123456789?" target="_blank"><img src="http://ad.doubleclick.net/ad/cThe mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 161, Column 431:
required attribute "type" not specified
…-><div id="ctvo_ctvCurrUrlP"><script>The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 166, Column 221:
ID "m1curling" already defined
…>Figure Skating</a></span><span id="m1curling"><a href="/curling/index.html">An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).
Line 23, Column 194:
ID "m1curling" first defined here
…"ctvo_first ">Hockey</a></li><li id="m1curling"><a href="/curling/index.html"…x.html">Curling</a></span><span id="m1hockey"><a href="/hockey/index.html">HoAn "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).
Line 23, Column 112:
ID "m1hockey" first defined here
…vel1Menu"><li class="ctvo_first" id="m1hockey"><a href="/hockey/index.html" c…an></div><div class="row"><span id="m1snowboard"><a href="/snowboard/index.htAn "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).
Line 23, Column 1573:
ID "m1snowboard" first defined here
…g </a></li> </ul> </div></li><li id="m1snowboard"><a href="/snowboard/index.h…imgml/template/ms_footer_2010.gif" /></div></div><script type="text/javascripThe attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 46, Column > 80:
XML Parsing Error: attributes construct error
…iv class="ctvo_masterCol8 ctvo_floatLeft "><div class="hslice "id="1">……iv class="ctvo_masterCol8 ctvo_floatLeft "><div class="hslice "id="1">…<h2 class="entry-title"style="display:none">Headlines</h2><h2 class="entry-title"style="display:none">Headlines</h2><h2 class="entry-title"style="display:none">Headlines</h2><a href="/webslices/library/_bridgePage_headlines.html"rel="feedurl"> </a><a href="/webslices/library/_bridgePage_headlines.html"rel="feedurl"> </a>…idgePage_headlines.html"rel="feedurl"> </a>…gin.<br /><img src='/imgml/get_flash_player.gif' alt='Flash Player' /></a></s……gin.<br /><img src='/imgml/get_flash_player.gif' alt='Flash Player' /></a></s……gin.<br /><img src='/imgml/get_flash_player.gif' alt='Flash Player' /></a></s……gin.<br /><img src='/imgml/get_flash_player.gif' alt='Flash Player' /></a></s……gin.<br /><img src='/imgml/get_flash_player.gif' alt='Flash Player' /></a></s……gin.<br /><img src='/imgml/get_flash_player.gif' alt='Flash Player' /></a></s……gin.<br /><img src='/imgml/get_flash_player.gif' alt='Flash Player' /></a></s……class="ctvo_box"><h2><span class="ctvo_titleLeft"> </span>Blogs & Features<sp……4"><div class="ctvo_box"><div class="ctvo_PreviewNews"><h2><span class="ctvo_……4"><div class="ctvo_box"><div class="ctvo_PreviewNews"><h2><span class="ctvo_……4"><div class="ctvo_box"><div class="ctvo_PreviewNews"><h2><span class="ctvo_……4"><div class="ctvo_box"><div class="ctvo_PreviewNews"><h2><span class="ctvo_……lls/pollid='+id+'/resultBlack.html?ThanksText='+ThanksText+'&ThanksUrl='+Than……lls/pollid='+id+'/resultBlack.html?ThanksText='+ThanksText+'&ThanksUrl='+Than… </div><div style="display:none"> </div></div> <div id="ctvo_FootContent"></div></body></html></div></body></html>